Sorry, np.find_common_type usage was only addressed in 2.0.x and won't be backported to 1.x: pandas-dev/pandas#53343

@bdice do you want to create another issue like #14160 for the numpy warnings (which we will also need to fix)? Or repurpose #14155 and leave it open after this PR merges, either is fine with me as long as we're tracking the work.

@bdice do you want to create another issue like #14160 for the numpy warnings (which we will also need to fix)? Or repurpose #14155 and leave it open after this PR merges, either is fine with me as long as we're tracking the work.

I don't have a strong opinion about how we resolve this -- maybe a new issue is best. But for now, I don't see a lot of benefit to fixing these warnings until we are ready to migrate cudf to pandas 2. Then it'll be easier to tell what usage is deprecated in cudf and not just what's deprecated in the pandas internals. If you want to figure that out, I'd appreciate help with filing a second issue (my plate is very full for today already).

But for now, I don't see a lot of benefit to fixing these warnings until we are ready to migrate cudf to pandas 2. Then it'll be easier to tell what usage is deprecated in cudf and not just what's deprecated in the pandas internals. If you want to figure that out, I'd appreciate help with filing a second issue (my plate is very full for today already).

I agree, I don't think we should work on this immediately. I just want an issue tracking this so that we don't forget to move the pin when we bump our pandas version. I'll open a stub issue for tracking that we can fill out with more info later.

Opened #14166

/merge